Level-two decryption associated with individual privacy and public safety protection via double encrypted lock box

ABSTRACT

A method substantially as shown and described the detailed description and/or drawings and/or elsewhere herein. A device substantially as shown and described the detailed description and/or drawings and/or elsewhere herein.

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§119, 120,121, or 365(c), and any and all parent, grandparent, great-grandparent,etc. applications of such applications, are also incorporated byreference, including any priority claims made in those applications andany material incorporated by reference, to the extent such subjectmatter is not inconsistent herewith.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC §119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

PRIORITY APPLICATIONS

-   -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. To Be Determined entitled RIGHT OF        INDIVIDUAL PRIVACY AND PUBLIC SAFETY PROTECTION VIA DOUBLE        ENCRYPTED LOCK BOX, naming Edward K. Y. Jung, Royce A. Levien,        Richard T. Lord, Robert W. Lord, and Mark Malamud, as inventors        filed 12 Jul. 2012, with attorney docket no. 0305-003-117-000000        which is currently co-pending or is an application of which a        currently co-pending application is entitled to the benefit of        the filing date.    -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/653,222 entitled LEVEL-ONE        ENCRYPTION ASSOCIATED WITH INDIVIDUAL PRIVACY AND PUBLIC SAFETY        PROTECTION VIA DOUBLE ENCRYPTED LOCK BOX, naming Edward K. Y.        Jung, Royce A. Levien, Richard T. Lord, Robert W. Lord, and Mark        Malamud, as inventors filed 16 Oct. 2012, with attorney docket        no. 0305-003-117A-000000 which is currently co-pending or is an        application of which a currently co-pending application is        entitled to the benefit of the filing date.    -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/660,848 entitled LEVEL-TWO        ENCRYPTION ASSOCIATED WITH INDIVIDUAL PRIVACY AND PUBLIC SAFETY        PROTECTION VIA DOUBLE ENCRYPTED LOCK BOX, naming Edward K. Y.        Jung, Royce A. Levien, Richard T. Lord, Robert W. Lord, and Mark        Malamud, as inventors filed 25 Oct. 2012, with attorney docket        no. 0305-003-117B-000000 which is currently co-pending or is an        application of which a currently co-pending application is        entitled to the benefit of the filing date.    -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation-in-part of U.S.        patent application Ser. No. 13/707,427 entitled PRE-EVENT        REPOSITORY ASSOCIATED WITH INDIVIDUAL PRIVACY AND PUBLIC SAFETY        PROTECTION VIA DOUBLE ENCRYPTED LOCK BOX, naming Edward K. Y.        Jung, Royce A. Levien, Richard T. Lord, Robert W. Lord, and Mark        Malamud, as inventors filed 6 Dec. 2012, with attorney docket        no. 0305-003-117C-000000 which is currently co-pending or is an        application of which a currently co-pending application is        entitled to the benefit of the filing date.

RELATED APPLICATIONS

NONE

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

SUMMARY

In one or more various aspects, a method includes but is not limited toreceiving a level-two encrypted output of a surveillance device;decrypting at least a part of the level-two encrypted output of thesurveillance device with a level-two decryption key that is practicablyinaccessible by a level-two encryption entity; and transmitting alevel-one encrypted output of the surveillance device. In addition tothe foregoing, other method aspects are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein-referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, computer programming, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer, and limited to patentablesubject matter under 35 USC 101.

In one aspect, a system includes but is not limited to a machineconfigured to create a physical reality of receiving a level-twoencrypted output of a surveillance device; a machine configured tocreate a physical reality of decrypting at least a part of the level-twoencrypted output of the surveillance device with a level-two decryptionkey that is practicably inaccessible by a level-two encryption entity;and a machine configured to create a physical reality of transmitting alevel-one encrypted output of the surveillance device. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the text (e.g.,claims and/or detailed description) and/or drawings of the presentdisclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent in thedisclosures set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a partially schematic diagram of an environment(s) and/oran implementation(s) of technologies described herein.

Figure A1 depicts a partially schematic diagram of an environment(s)and/or an implementation(s) of technologies described herein.

FIGS. 2-7 illustrate system/operational descriptions of implementations.

The use of the same symbols in different drawings typically indicatessimilar or identical items unless context dictates otherwise.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

As a courtesy to the reader, and with reference now to the accompanyingfigures herein, in general “100 series” reference numerals willtypically refer to items first introduced/described by FIG. 1, “200series” reference numerals will typically refer to items firstintroduced/described by FIG. 2, “300 series” reference numerals willtypically refer to items first introduced/described by FIG. 3, etc.

The present application uses formal outline headings for clarity ofpresentation. However, it is to be understood that the outline headingsare for presentation purposes, and that different types of subjectmatter may be discussed throughout the application (e.g.,device(s)/structure(s) may be described under process(es)/operationsheading(s) and/or process(es)/operations may be discussed understructure(s)/process(es) headings; and/or descriptions of single topicsmay span two or more topic headings). Hence, the use of the formaloutline headings is not intended to be in any way limiting.

I. Overview: Operational/Functional Language Herein DescribesMachines/Machine Control/Machine-Controlled Processes Unless ContextDictates Otherwise

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled in the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for massively complex computational machinesor other means. As discussed in detail below, the operational/functionallanguage must be read in its proper technological context, i.e., asconcrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to the human reader. Thedistillation also allows one of skill in the art to adapt theoperational/functional description of the technology across manydifferent specific vendors' hardware configurations or platforms,without being limited to specific vendors' hardware configurations orplatforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail herein, these logicaloperations/functions are not representations of abstract ideas, butrather are representative of static or sequenced specifications ofvarious hardware elements. Differently stated, unless context dictatesotherwise, the logical operations/functions will be understood by thoseof skill in the art to be representative of static or sequencedspecifications of various hardware elements. This is true because toolsavailable to one of skill in the art to implement technical disclosuresset forth in operational/functional formats—tools in the form of ahigh-level programming language (e.g., C, java, visual basic), etc.), ortools in the form of Very High speed Hardware Description Language(“VHDL,” which is a language that uses text to describe logiccircuits)—are generators of static or sequenced specifications ofvarious hardware configurations. This fact is sometimes obscured by thebroad term “software,” but, as shown by the following explanation, thoseskilled in the art understand that what is termed “software” is ashorthand for a massively complex interchaining/specification ofordered-matter elements. The term “ordered-matter elements” may refer tophysical components of computation, such as assemblies of electroniclogic gates, molecular computing logic constituents, quantum computingmechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. See, e.g., Wikipedia, High-level programming language,http://en.wikipedia.org/wiki/High-level_programming_language (as of Jun.5, 2012, 21:00 GMT). In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages. See, e.g., Wikipedia, Natural language,http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00GMT).

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood by a human reader). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices), molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of logic, such asBoolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT).

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute a shorthand that specifies theapplication of specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configurations, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). See, e.g.,Wikipedia, Instructions per second,http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5,2012, 21:04 GMT). Thus, programs written in machine language—which maybe tens of millions of machine language instructions long—areincomprehensible to most humans. In view of this, early assemblylanguages were developed that used mnemonic codes to refer to machinelanguage instructions, rather than using the machine languageinstructions' numeric values directly (e.g., for performing amultiplication operation, programmers coded the abbreviation “mutt,”which represents the binary number “011000” in MIPS machine code). Whileassembly languages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thatuseful, tangible, and concrete work is done. For example, as indicatedabove, such machine language—the compiled version of the higher-levellanguage—functions as a technical specification which selects outhardware logic gates, specifies voltage levels, voltage transitiontimings, etc., such that the useful work is accomplished by thehardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality of logic(s), or (d) virtually any combination of theforegoing. Indeed, any physical object which has a stable, measurable,and changeable state may be used to construct a machine based on theabove technical description. Charles Babbage, for example, constructedthe first mechanized computational apparatus out of wood with themechanism powered by cranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language should not be taken as an indicationthat such functional/operational technical descriptions are abstractideas, or mere expressions of abstract ideas. In fact, as outlinedherein, in the technological arts this is simply not true. When viewedthrough the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

II. Panoptic System and Method Architectures

With reference now to the Figures and with reference now to FIG. 1, FIG.1 shows a partially schematic diagram of an environment(s) and/or animplementation(s) of technologies described herein. FIG. 1 depictsatypical person 100 resident within the confines of Room 101 of the CatoInstitute. FIG. 1 illustrates that Room 101 of the Cato Institute issurveilled by camera 102, where camera 102 has an associated identifier(e.g., name) of “Skynet Security Camera Alpha.”

FIG. 1 illustrates that Camera-to-Obscure Co. Circuitry 104 creates apseudo-public-private key pair. FIG. 1 shows that Camera-to-Obscure Co.Circuitry 104 transmits Camera-to-Obscure Co. generated Pseudo-PublicKey to Skynet Name Obscuring Unit 106. FIG. 1 depicts that the output ofSkynet Name Obscuring Unit 106 is “Encrypted-Camera-ID” which is astring that results from encrypting “Skynet Security Camera Alpha” withthe pseudo-public key delivered to Skynet Name Obscuring Unit 106 byCamera-to-Obscure Co. Circuitry 104. FIG. 1 further depicts thatCamera-to-Obscure Co. Circuitry 104 transmits Camera-to-Obscure Co.generated Pseudo-Private Key to FBI Name DE-Obscuring Circuitry 136,which as show herein, in one implementation, will subsequently attemptto unlock various received encrypted names by trying to decrypt thereceived encrypted names via trying various pseudo-private keys on theFBI Name DE-Obscuring Circuitry 136's private key chain until theencrypted name is unlocked; that is, in a fashion analogous to a humantrying similar looking keys on his key chain to find the key that opensthe front door to his house. In other implementations FBI NameDE-Obscuring Circuitry 136 uses a Unique Camera-to-Obscure Co. Key pairdesignator (not shown), analogous to the ways unique key pairdesignators are used as described elsewhere herein with respect to, forexample, the pseudo-public-private key pairs respectively generated byCyberdine Protective Services and Heuristic Algorithm Services such asdescribed herein; such alternate implementations for the FBI NameDE-Obscuring Circuitry 136 that use a Unique Camera-to-Obscure Co. Keypair designator are not shown in the drawings for sake of clarity butcan be understood in light of at least the reference examples herein.

FIG. 1 illustrates that Skynet Name Obscuring Unit 106 transmitsoutput—“Encrypted-Camera-ID”—which is the string that is the result ofencrypting “Skynet Security Camera Alpha” with the pseudo-public key ofthe pseudo-public-private key pair generated by Camera-to-Obscure Co.circuitry 104—plus a date and time window for which “Encrypted-CameraID” is good (e.g., 16 June 2014 from 10:00 a.m. to 11:00 a.m.) to SkynetLevel One Encryption Circuitry 110. In some implementations, the dateand time is optional, and Skynet Level One Encryption Circuitry 110 justappends the appropriate date and time during which CCD output 112 isreceived from camera 102.

FIG. 1 shows that in one implementation CCD output 112 from camera 102feeds—via a hardwired connection—directly into Skynet Level OneEncryption Circuitry 110 as a stream—not a frame. Thus, in oneimplementation such as illustrated herein, at no point can camera 102'soutput be intelligibly accessed until/unless several different legalentities—controlling very different encryption/decryption automation thekeys to which encryption/decryption are at no time held by a singleparty who can decrypt and see the camera output—work in a transparentand coordinated fashion.

FIG. 1 shows atypical person 100 (e.g., one with an alternativelifestyle) who just wants to be left alone but is aware that camera102—“Skynet Security Camera Alpha”—is surveilling Room 101 of the CatoInstitute where atypical person 100 is resident. Accordingly, atypicalperson 100 is depicted as saying “respect my privacy, and keep yourintrusive cameras off my body!”

In one implementation, the public safety is served by constant camerasurveillance of Room 101 of the Cato Institute, but atypical person 100has legitimate concerns as to how such surveillance data might be used.To allay atypical person 100's concerns, illustrated is that CCD output112 of camera 102 is clocked directly into Skynet Level One EncryptionCircuitry 110 as a stream (e.g., such that it can't typically be viewedas video data), which in one implementation immediately encrypts thestream of CCD output 112 using a pseudo-public key generated byCyberdine-Protective-Services Key-Pair Generation Automation 114.

Continuing to refer to FIG. 1, illustrated is thatCyberdine-Protective-Services Key-Pair Generation Automation 114 createspseudo-public-private key pairs. Shown is thatCyberdine-Protective-Services Key-Pair Generation Automation 114delivers the pseudo-public key along with a UniqueCyberdine-Protective-Services Key Pair Designator to Skynet Level OneEncryption Circuitry 110 (as show herein UniqueCyberdine-Protective-Services Key Pair Designator will ultimately beutilized to coordinate the pseudo-public and pseudo-private keys by twodifferent and unique legal entities; that is, the unique designator willallow different entities, which are “blind” to the pairing of thepseudo-public and pseudo-private keys, to subsequently use the correctpseudo-private key to decrypt that which was encoded with thecorresponding pseudo-public key). Skynet Level One Encryption Circuitry110 is depicted as under the legal control and administration of SkynetSecurity Company.

FIG. 1 shows that Cyberdine-Protective-Services Key-Pair GenerationAutomation 114 delivers the pseudo-private key along with a uniqueCyberdine-Protective-Services Key Pair Designator which serves toidentify the pseudo-public-private key pair of which the pseudo-privatekey forms a part to Federal Bureau of Investigation (“FBI”) Level OneDEcryption Circuitry 130.

FIG. 1 illustrates that while Cyberdine Protective Services has legalcontrol and administration of both keys of the pair, as well as theCyberdine-Generated Unique Key Pair Designator which serves toidentify/coordinate the key pair, Cyberdine Protective Services does nothave access to CCD output 112 of camera 102. FIG. 1 shows that whenSkynet Level One Encryption Circuitry 110 encrypts CCD output 112 ofcamera 102 with the Cyberdine-Security-Services generated pseudo-publickey, Skynet has no legal control, administration, or possession of thecorresponding Cyberdine-Security-Services generated pseudo-private keywhich could be used to unlock the encryption of CCD output 112 of camera102 that was/is instantiated by Skynet Level One Encryption Circuitry110. Cyberdine-Protective-Services Key-Pair Generation Automation 114 isdepicted as under the legal control and administration of CyberdineProtective Services Company which is separate and apart from SkynetSecurity Company.

FIG. 1 illustrates that the system ensures that Skynet Security Companycannot see any image because it only holds the pseudo-public key of apseudo-public-private key pair that has been generated by another legalentity, Cyberdine Protective Services Company.

FIG. 1 shows that, in one implementation, Skynet Level One EncryptionCircuitry 110, after receipt of “Encrypted-Camera-ID” which is thestring that is result of encrypting “Skynet Security Camera Alpha” plusa date and time window for which “Encrypted-Camera ID” is good (e.g., 16June 2014 from 10:00 a.m. to 11:00 a.m.) from Skynet Name Obscuring Unit106, encrypts CCD output 112 of camera 102 that occurred on 16 June 2014from 10:00 a.m. to 11:00 a.m. via the pseudo-public key of thepseudo-public-private key pair generated by Cyberdine ProtectiveServices Company. Thereafter, illustrated is that Skynet Level OneEncryption Circuitry 110 associates the Level One encryption of CCDoutput 112 of camera 102 with meta-data composed of‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.”+“Unique Cyberdine-Protective-Services Key Pair Designator.”’ Inthe instance shown, the ‘“Encrypted-Camera-ID”+“Date: 16 June 2014;Time: 10:00 a.m.-11:00 a.m.”+“Unique Cyberdine-Protective-Services KeyPair Designator”’ meta-data is kept outside the Level One encryptionapplied by Skynet Level One Encryption Circuitry 110, but those skilledin the art will appreciate that in other implementations all or part ofsuch meta-data may be emplaced inside the Level One encryption.

FIG. 1 shows that, subsequently, Skynet Level One Encryption Circuitry110 sends Level One encrypted CCD output 118, and its associatedmeta-data of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00a.m.-11:00 a.m.”+“Unique Cyberdine-Protective-Services Key PairDesignator”’ to Skynet Level Two Encryption Circuitry 120. FIG. 1depicts that upon receipt of Level One Encrypted CCD output 118, SkynetLevel Two Encryption Circuitry 120 encrypts the received Level OneEncrypted CCD output 118 as well as its associated meta-data of‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.”+“Unique Cyberdine-Protective-Services Key Pair Designator”’ usinga pseudo-public key of a pseudo-public-private key pair that has beengenerated by another legal entity, Heuristic-Algorithm Services, thuscreating a Level Two encryption of Level One Encrypted CCD output 118.With reference now back to CCD output 112 of camera 102 at this pointFIG. 1 shows that the Level Two encryption of Level One Encrypted CCDoutput 118 is a doubly-encrypted version of CCD output 112 of camera102.

FIG. 1 illustrates that the system ensures that Skynet Level TwoEncryption Circuitry 120 can only encrypt because it holds only thepseudo-public key of a pseudo-public-private key pair that has beengenerated by yet another legal entity, Heuristic-Algorithm Services.FIG. 1 shows that Heuristic-Algorithm Services also generates a “UniqueHeuristic-Algorithm-Services Key Pair Designator” that will subsequentlybe used to “pair” the correct pseudo-private key with the correctpseudo-public key by separate legal entities that are effectively“blind” to the pairing done by Heuristic-Algorithm Services. As shownherein, the pseudo-public-private key pairs and the UniqueHeuristic-Algorithm-Services Key Pair Designator are generated byHeuristic-Algorithm-Services Key Pair Generation Automation 127, whichis under the legal control and administration of Heuristic-AlgorithmServices Company.

Illustrated is that Skynet Security Level Two Encryption Circuitry 120thereafter associates the meta-data of ‘“Encrypted-Camera-ID”+“Date: 16June 2014; Time: 10:00 a.m.-11:00 a.m.”+“UniqueHeuristic-Algorithm-Services Key Pair Designator”’ with the Level TwoEncrypted CCD output 121.

Thereafter, illustrated is that Skynet Security Level Two EncryptionCircuitry 120 sends the Level Two encrypted CCD output 121, havingassociated meta-data of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014;Time: 10:00 a.m.-11:00 a.m.”+“Unique Heuristic-Algorithm-Services KeyPair Designator”’ to PreCrime Repository 122. The neologism “PreCrime”is used herein for sake of illustration, and may be understood asrepresentative of a “pre-event-of-interest” concept.

Shown is that PreCrime Repository Double-Locked Box Storage Engine 124receives the Level Two Encrypted CCD Output 121, having associatedmeta-data of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00a.m.-11:00 a.m.”+“Unique Heuristic-Algorithm-Services Key PairDesignator”’ which is then stored as a doubly-encrypted CCD outputlockbox indexed by some or all of its meta-data (e.g., indexed by someor all of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10a.m.-11:00 a.m.”+“Unique Heuristic-Algorithm-Services Key PairDesignator”’). In alternate implementations Level Two Encrypted CCDOutput 121 is indexed by “Encrypted-Camera-ID” alone, while in otheralternate implementations the Level Two encrypted data is indexed by“Unique Heuristic-Algorithm-Services Key Pair Designator” alone, butFIG. 1 shows meta-data of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014;Time: 10:00 a.m.-11:00 a.m.”+“Unique Heuristic-Algorithm-Services KeyPair Designator”’ being used to index for sake of clarity.

It is expected that, in a free society in most instances thedoubly-encrypted version of CCD output 112 of camera 102 (e.g., LevelTwo Encrypted CCD Output 121) will never be retrieved and decrypted.That said, it is expected that in some instances public safety mightdemand that the doubly-encrypted version of CCD output 112 of camera 102be retrieved and decrypted. For sake of illustration, such an examplewill now be discussed.

Referring now to the lower left corner of FIG. 1, FIG. 1 depicts, forsake of example, Judge Judy acting subsequent to the event of a crime(e.g., a terrorist attack) committed in the vicinity of Room 101 of theCato Institute at some time between 10:00 a.m. and 10:45 a.m. on 16 June2014. FIG. 1 illustrates the Department of Justice asking 160 Judge Judyto issue an order for the unlocking of the camera output from 10:00 a.m.and 10:45 a.m. on 16 June 2014 that is associated with a view of Room101 of the Cato Institute at the time in question. At this point,neither the Department of Justice nor Judge Judy has a name identifyingthe camera in question. In response, FIG. 1 shows Judge Judy's machine166 asking 162 the Department of Treasury Encrypted Camera ID+CameraLocation Repository Circuitry 163 (Camera-to-Obscure Co and/or SkynetSecurity Company is shown as having delivered such information toTreasury at or around the time of such output's creation) for the“Encrypted-Camera-ID” that is associated with the camera that wasviewing Room 101 of the Cato Institute on the date of 16 June 2014,between the times of 10:00 a.m. and 10:45 a.m.

In response, FIG. 1 shows the Department of Treasury Encrypted CameraID+Camera Location Repository Circuitry 163 transmitting 164 to JudgeJudy's machine 166 the “Encrypted-Camera-ID” that is associated with thecamera at Room 101 of the Cato Institute for the date of 16 June 2014,between the times of 10:00 a.m. and 10:45 a.m. (e.g. the output ofcamera 102 from 10:00 a.m. to 11:00 a.m. that the system stored). FIG. 1depicts that Skynet Name Obscuring Unit 106 is shown as havingtransmitted to Department of Treasury Encrypted Camera ID+CameraLocation Repository Circuitry 163 the “Encrypted-Camera-ID” that isassociated with the camera having geographic location of Room 101 of theCato Institute for the date of 16 June 2014, and between the times of10:00 a.m. and 11:00 a.m. at or around the time “Encrypted Camera ID”was created. That is, at some point prior to Judge Judy's machine 166making the request.

FIG. 1 depicts that, subsequent to receiving “Encrypted-Camera-ID” thatis associated with the camera that was surveilling Room 101 of the CatoInstitute on the date of 16 June 2014, and between the times of 10:00a.m. and 11:00 a.m. (the encrypted envelope that holds the time ofinterest of 10:00 a.m. to 10:45 a.m.), Judge Judy's machine 166transmits to Department of Justice Machine 168 an order directing thatthe output of “Encrypted-Camera-ID” associated with the camera at Room101 of the Cato Institute for the date of 16 June 2014, between thetimes of 10:00 a.m. and 11:00 a.m. be unlocked. FIG. 1 illustrates thatDepartment of Justice Machine 168 transmits messages to HomelandSecurity Doubly-Encrypted Lockbox Retrieval Circuitry 180, HomelandSecurity Level Two DEcryption Circuitry 128, and FBI Level OneDEcryption Circuitry 130 directing the retrieval and/or unlocking of thedoubly-encrypted lockbox associated with “Encrypted-Camera-ID” for thedate of 16 June 2014, between the times of 10:00 a.m. and 11:00 a.m.

Referring now to the approximate middle-right portion of FIG. 1, FIG. 1illustrates that, in response to Judge Judy's order the content of whichwas relayed through the message of Department of Justice Machine 168,Homeland Security Doubly-Encrypted Lockbox Retrieval Circuitry 180 asksPreCrime Repository Circuitry 122 for the files indexed by‘“Encrypted-Camera-ID”; “Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.”’ More specifically, FIG. 1 shows that Homeland SecurityDoubly-Encrypted Lockbox Retrieval Circuitry 180 transmits a request forthe double-encrypted lockbox files having index of‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.”’ to PreCrime Repository Doubly-Encrypted CCD Output RetrieverEngine 126.

FIG. 1 depicts PreCrime Repository Doubly-Encrypted CCD Output RetrieverEngine 126 pulling the doubly-encrypted files indexed by‘“Encrypted-Camera-ID”+Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.+“Unique Heuristic-Algorithm Services Key Pair Designator”’ fromwithin PreCrime Repository 122. FIG. 1 illustrates that thereafterPreCrime Repository Doubly-Encrypted CCD Output Retriever Engine 126sends Level Two Encrypted CCD output 121 along with the associatedmeta-data of ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00a.m.-11:00 a.m.”+“Unique Heuristic-Algorithm Services Key PairDesignator”’ to Homeland Security Level Two DEcryption Circuitry 128,which, in view of Judge Judy's order, upon receipt decrypts the receivedLevel Two Encrypted CCD output 121 with the correct pseudo-private keygenerated by Heuristic Algorithm Services. In one implementation,Homeland Security Level Two DEcryption Circuitry 128 is able to retrievethe correct pseudo-private key to do the decryption via use of UniqueHeuristic-Algorithm-Services Key Pair Designator which was previouslydelivered—by Heuristic-Algorithm Services Key-Pair Generation Automation127—to Homeland Security Level Two DEcryption Circuitry 128 inassociation with the pseudo-private key that unlocks the correspondingpseudo-public key that was previously used by Skynet Level TwoEncryption Circuitry 120 to encrypt as described herein. Thus, in oneimplementation Unique Heuristic-Algorithm-Services Key Pair Designatoris used to retrieve the correct decryption key, even though thedecryptor never had possession/control of the Heuristic-Algorithmpseudo-public key that was used to encrypt.

FIG. 1 shows that Homeland Security Level Two DEcryption Circuitry 128uses the pseudo-private encryption key of Heuristic-Algorithm Servicesthat is identified by Unique Heuristic-Algorithm-Services Key PairDesignator—which accompanies the doubly encrypted lockbox asmeta-data—to undo the Level Two encryption that was previouslyinstantiated by Skynet Level Two Encryption Circuitry 120. Depicted isthat in one implementation the decryption yields the Level-TwoDecrypted-Level One Encrypted CCD output data 129 (e.g., the Level TwoDecryption applied by Skynet Level Two Encryption Circuitry 120 has beenunlocked but the data is still encrypted via the Level One encryptionpreviously applied by Skynet Level One Encryption Circuitry 110) andfurther depicted is that the decryption done by Homeland Security LevelTwo Decryption Circuitry 128—accomplished via retrieval of the correctkey identified by the Unique Heuristic-Algorithm Services Key PairIdentifier—also provides as output the successful decryption of theUnique Cyberdine-Protective-Services Key Pair Designator (which as shownherein had previously been encrypted by Skynet Level Two EncryptionCircuitry 120). FIG. 1 depicts that thereafter Homeland Security LevelTwo DEcryption Circuitry 128 associates as meta-data‘“Encrypted-Camera-ID”+Date: 16 June 2014; Time: 10:00 a.m.-11:00a.m.”+“Unique Cyberdine-Protective-Services Key Pair Designator”’ withthe Level-Two Decrypted-Level One Encrypted CCD output data 129 (whichis still encrypted via the level one encryption previously applied bySkynet Level One Encryption Circuitry 110). FIG. 1 illustrates thatHomeland Security Level Two DEcryption Circuitry 128 thereafter sendsthe meta-data ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time: 10:00a.m.-11:00 a.m.”+“Unique Cyberdine-Protective-Services Key PairDesignator”’ in association with the with the Level Two Decrypted-LevelOne Encrypted CCD output data 129 (which is still encrypted via thelevel one encryption previously applied by Skynet Level One EncryptionCircuitry 110) to FBI Level One Decryption Circuitry 130.

FIG. 1 shows that, FBI Level One DEcryption Circuitry 130 receives themeta-data ‘“Encrypted-Camera-ID”+“Date: 16 June 2014; Time 10:00a.m.-11:00 a.m.”+“Unique Cyberdine-Protective-Services Key PairDesignator”’ in association with the Level-Two Decrypted-Level OneEncrypted CCD output data 129 (which is still encrypted via the levelone encryption previously applied by Skynet Level One EncryptionCircuitry 110). FIG. 1 depicts that FBI Level One DEcryption Circuitry130 determines that Judge Judy's order, as related through the messageof Department of Justice Machine 168, indicates that the data associatedwith “Encrypted-Camera-ID” is to be unlocked. Accordingly, FIG. 1illustrates that FBI Level One DEcryption Circuitry 130 uses thereceived Unique Cyberdine-Protective-Services Key Pair Designator toretrieve the correct Cyberdine-Protective-Services pseudo-private keythat corresponds to the Cyberdine-Protective-Services pseudo-public keythat Skynet Level One Encryption Circuitry 110 used to encrypt CCDOutput 112. FIG. 1 shows that FBI Level One DEcryption Circuitry 130uses the retrieved Cyberdine-Protective-Services pseudo-private key tounlock the Level One encryption. Thus, FIG. 1 shows FBI Level OneDEcryption Circuitry 130 outputting doubly-decrypted CCD output 132(e.g., the in-the-clear stream of CCD output 112 of camera 102).

FIG. 1 depicts that Stream-to Viewable-CCD Output Conversion Circuitry134 converts the stream to viewable CCD output (e.g., still or motionimage frames) which is securely displayed in Judge Judy's chambers.Depicted is that for an additional level of citizen's right'sprotection, “Encrypted-Camera-ID” is sent by FBI Level One DEcryptionCircuitry 130 to FBI Name DE-Obscuring Circuitry 136 which then, using apseudo-private key of a pseudo-public-private key pair generated bysoftware created by Camera-to-Obscure Co., decrypts“Encrypted-Camera-ID” to “Skynet Security Camera Alpha” which is thenused by Stream-to Viewable-CCD Output Conversion Circuitry 134 toassociate the name of the camera with the viewable CCD output.

FIG. 1 illustrates Judge Judy in her Chambers viewing the output of“Skynet Security Camera Alpha” Video of 10:00 a.m. to 10:45 a.m. thatwas captured on 16 June 2014. Depicted is that Judge Judy determinesthat atypical person 100 has done nothing wrong, and concludes that theDepartment of Justice need not see the output. Thus, FIG. 1 shows JudgeJudy denying the Department of Justice's request to see the output ofthe camera viewing Room 101 of the Cato Institute for the date of 16June 2014 and time from 10:00 a.m. to 10:45 a.m.

Thus as shown herein, atypical citizen 100's rights to privacy, as wellas the public's right to safety, are thus protected and/or balanced bythe disclosed technologies.

III. Synoptic System and Method Architectures

Figure A1 depicts a partially schematic diagram of an environment(s)and/or an implementation(s) of technologies described herein. Thecomponents of Figure A1 are described in context herein.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

As a courtesy to the reader, and with reference now to the accompanyingfigures herein, in general “100 series” reference numerals willtypically refer to items first introduced/described by FIG. 1, “200series” reference numerals will typically refer to items firstintroduced/described by FIG. 2, “300 series” reference numerals willtypically refer to items first introduced/described by FIG. 3, etc.

Referring now to FIG. 2, Fig. A1, and FIG. 1, such figures depictsystem/operational descriptions of implementations. Operation 200 showsthe start of the depiction of the system/operational implementations.Operation 202 illustrates receiving a level-two encrypted output of asurveillance device (e.g., receiving (e.g., via Homeland Security LevelTwo Decryption Circuitry 128) a level-two encrypted output of asurveillance device (e.g., level-two encrypted CCD output 121 of camera102)). Operation 204 shows decrypting at least a part of the level-twoencrypted output of the surveillance device with a level-two decryptionkey that is practicably inaccessible by a level-two encryption entity(e.g., decrypting (e.g., via Level Two Sighted DEcryption Circuitry D100of Homeland Security Level Two DEcryption Circuitry 128) at least a partof the output of the level-two encrypted output of the surveillancedevice (e.g., at least a part of level-two encrypted CCD output 121)with a level-two decryption key that is practicably inaccessible by alevel-two encryption entity (e.g., Heuristic Algorithm ServicesPseudo-Private key D102 which could be a DEcryption key that can be usedto DEcrypt at least a part of level-two encrypted CCD output 121 ofcamera 102 of which Skynet Level Two Encryption Circuitry 120 has/had noknowledge when it encrypted with the corresponding encryption key (e.g.,Heuristic Algorithm Services Pseudo-Public Encrytpion Key) and for whichthere is no practicable way by which Skynet Level Two EncryptionCircuitry 120 (or its owner/administrator Skynet) can obtain suchunlocking key; that is, a companion decryption key to that encryptionkey that gave Skynet Level Two Encryption Circuitry 120 the ability toencrypt but without having given Skynet Level Two Encryption Circuitry120 the ability to decrypt that which it has encrypted)). Operation 206depicts transmitting a level-one encrypted output of the surveillancedevice (e.g., transmitting (e.g., via Level Two Decrypted TransmissionCircuitry D104 of Homeland Security Level Two DEcryption Circuitry 128)a level-two DEcrypted output of the surveillance device (e.g., Level-TwoDecrypted-Level-One Encrypted CCD output 129, which in the describedexample is what is exposed when the level-two encryption is unwrapped)).

Operation 208 shows the end of the depiction of the system/operationaldescriptions of implementations.

Referring now to FIG. 3, FIG. 2, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 3shows that operation 202—receiving a level-two encrypted output of asurveillance device—may include a number of alternate/additionalcomponent operations. Operation 300 depicts accepting an output of apre-event repository (e.g., accepting (e.g., via Homeland Security LevelTwo DEcryption Circuitry 128) an encrypted output of a surveillancedevice (e.g., a level two encrypted version, earlier created by SkynetLevel Two Encryption Circuitry 120 and subsequently stored by PreCrimeRepository Double-Locked Box Storage Engine 124 within the circuitry ofPreCrime Repository 122), of at least a part of an image capture portion(e.g., video capture of camera 102) or an audio surveillance portion(e.g., a sound capture portion of camera 102) that is sent by PreCrimeRepository Doubly-Encrypted CCD Output Retriever Engine 126 of PreCrimeRepository 122).

Operation 302 illustrates accepting a level-two encrypted version of anoutput of at least one of an image surveillance device, an audiosurveillance device, a motion surveillance device, or a tactilesurveillance device (e.g., accepting (e.g., via Homeland Security LevelTwo DEcryption Circuitry 128) via the intermediary of Pre-CrimeRepository 122 an output (e.g., digital or analog data) of Skynet LevelTwo Encryption Circuitry 120 that constitutes a level-one encryptedversion of at least one of an image surveillance device (e.g., a videocapture portion of camera 102), an audio surveillance device (e.g., anaudio capture portion of camera 102), a motion surveillance device(e.g., a commercially available motion detector (not shown)) or atactile surveillance device (e.g., a commercially available vibrationdetector (not shown))).

Operation 304 shows accepting the level-two encrypted output of thesurveillance device in a form such that the level-two encrypted outputof the surveillance device is substantially unusable absent combinationwith other information not present in the level-two encrypted output ofthe surveillance device (e.g., accepting (e.g., via Homeland SecurityLevel Two DEcryption Circuitry 128) the level-two encrypted output ofthe surveillance device (e.g., level-two encrypted CCD output 121 ofcamera 102) in a form such that the output of the surveillance device issubstantially unusable absent combination with other information notpresent in the output of the surveillance device (e.g., as described inrelation to FIG. 1 and/or A1 Homeland Security Level-Two EncryptionCircuitry 128 may accept from PreCrime Repository 122 a packet having anencrypted output of a surveillance device (e.g., level-two encrypted CCDoutput 121 of camera 102) that is substantially unusable absent thedecryption key (e.g., Heuristic-Algorithm Services Pseudo-PrivateDecryption Key D102) that would unlock the encryption key (e.g.,Heuristic-Algorithm-Services Pseudo-Public Encryption Key) that was usedto create an encrypted output of the surveillance device (e.g., used bySkynet Level-Two Encryption Circuitry 120 to produce Level-Two encryptedCCD output 121 of camera 102))). Other operations of FIG. 3 depict othersystem/operational descriptions of implementations as described herein.

Referring now to FIG. 4, FIG. 3, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 4shows that operation 304—accepting the level-two encrypted output of thesurveillance device in a form such that the level-two encrypted outputof the surveillance device is substantially unusable absent combinationwith other information not present in the level-two encrypted output ofthe surveillance device—may include a number of alternate/additionalcomponent operations. Operation 400 depicts accepting an output of apre-event repository, the output associated with a level-two encryptionwhich cannot practicably be decrypted by a level-two encryption entity(e.g., as described in relation to FIG. 1 and/or Fig. A1 HomelandSecurity Level Two Decryption Circuitry 128 may accept an encryptedoutput of a surveillance device (e.g., level-two encrypted CCD output121 of camera 102) that is substantially unusable absent the decryptionkey (e.g., Heuristic-Algorithm-Services Pseudo-Private DEcryption KeyD102) that would unlock the encryption key (e.g.,Heuristic-Algorithm-Services Pseudo-Public Encryption Key) used tocreate the encrypted output of the surveillance device (e.g., level-twoencrypted CCD output 121 of camera 102; furthermore, as described hereinSkynet Level-Two Encryption Circuitry 120 encrypts with an encryptionkey (e.g., Heuristic-Algorithm-Services Pseudo-Public Encryption Key)the paired decryption key of which Skynet Level-Two Encryption Circuitry120 has no practicable way of obtaining in thatHeuristic-Algorithm-Services Key-Pair Generation Automation 127 activelywithholds the decryption key (e.g., paired Heuristic-Algorithm ServicesPseudo-Private Decryption Key D102) from Skynet Level Two EncryptionCircuitry 120).

Operation 402 illustrates accepting an output of a pre-event repository,the output associated with a level-two key-pair generation entity (e.g.,as described herein Homeland Security Level Two Decryption Circuitry 128may accept from Pre-Crime Repository 122 a data block having Level TwoEncrypted CCD Output 121 that Skynet Level Two Encryption Circuitry 120had earlier produced by encrypting with an encryption key (e.g.,Heuristic-Algorithm Services Pseudo-Public Encryption Key) the paireddecryption key of which Skynet Level Two Encryption Circuitry 120 has nopracticable way of obtaining in that Heuristic-Algorithm-ServicesKey-Pair Generation Automation 127 actively withholds the decryption key(e.g., paired Heuristic-Algorithm-Services Pseudo-Private DecryptionKey) from Skynet Level Two Encryption Circuitry 120; furthermore, asalso described herein, Heuristic-Algorithm-Services Key-Pair GenerationAutomation 127 creates a pseudo-public-private key pair, where thepseudo-public key is delivered—along with a Heuristic-Algorithm ServicesUnique Key-Pair Designator—to Skynet Level Two Encryption Circuitry 120and where the corresponding pseudo-private key (e.g., pairedHeuristic-Algorithm-Services Pseudo-Private Decryption Key) isdelivered—along with the Heuristic-Algorithm Services Unique Key-PairDesignator—to Homeland Security Level Two DEcryption circuitry 128).

Operation 404 illustrates that operation 402—accepting an output of apre-event repository, the output associated with a level-two key-pairgeneration entity—may include a number of alternate/additional componentoperations. Operation 404 depicts accepting an output of a pre-eventrepository, the output associated with a decryption key generated by alevel-two key-pair generation entity (e.g., as described herein HomelandSecurity Level Two DEcryption Circuitry 128 accepts from PreCrimeRepository 122 a Level-Two Encrypted CCD output 121 that was producedwhen Skynet Level-Two Encryption Circuitry 120 encrypted with anencryption key (e.g., Heuristic-Algorithm-Services Pseudo-PublicEncryption Key) the paired decryption key of which was generated by alevel-two key-pair generation entity (e.g., Heuristic AlgorithmServices, an entity that legally owns/administratesHeuristic-Algorithm-Services Key-Pair Generation Automation 127)); asalso described herein, Heuristic-Algorithm-Services Key-Pair GenerationAutomation 127 creates a pseudo-public-private key pair, where thepseudo-public key is delivered to Skynet Level Two Encryption Circuitry120 and where the corresponding pseudo-private key is delivered toHomeland Security Level Two DEcryption Circuitry 128 (in one instancethe encryption key itself functions analogous to, or in some instancesas, a Heuristic-Algorithm Services Unique Key-Pair Designator in thatHomeland Security Level Two DEcryption Circuitry 128 finds thecorresponding decryption key (e.g., Heuristic Algorithm ServicesPseudo-Private Decryption Key) by trying the keys on its keychain untila practicably useable decryption occurs (e.g., such as one of severalclear text strings, appended by Skynet Level Two Encryption Circuitry120 to level-one encrypted CCD output 118 before such is encrypted intoLevel-Two Encrypted CCD Output 121 by Skynet Level Two EncryptionCircuitry 120, which will subsequently allow Homeland Security Level TwoDecryption Circuitry 128 to determine that it has used the right key todecrypt (e.g., such as by the appended plain text string beingrecognized after the level two decryption (also, in otherimplementations, a hash of the string to-be-encrypted by level twoencryption circuitry is applied prior to level two encryption and thedecryption automation calculates a like hash upon decryption todetermine if the right decryption key has been used (the right key beingthat which correctly unlocks the encryption such that thecorrect/recognizable hash is generated when the hashing function is runupon the decrypted string))).

Operation 406 illustrates that operation 402—accepting an output of apre-event repository, the output associated with a level-two key-pairgeneration entity—may include a number of alternate/additional componentoperations. Operation 406 depicts accepting an output of a pre-eventrepository, the output associated with a key-pair designator generatedby a level-two key-pair generation entity (e.g., as described hereinHomeland Security Level Two DEcryption Circuitry 128 accepts Level-TwoEncrypted CCD output 121 that was produced when Skynet Level-TwoEncryption Circuitry 120 encrypted with an encryption key (e.g.,Heuristic-Algorithm-Services Pseudo-Public Encryption Key) the paireddecryption key of which was generated by a level-two key-pair generationentity (e.g., Heuristic-Algorithm Services, an entity that legallyowns/administrates Heuristic-Algorithm Services Key-Pair GenerationAutomation 127); as also described herein, Heuristic-Algorithm ServicesKey-Pair Generation Automation 127 creates a pseudo-public-private keypair, where the pseudo-public key is delivered—along with aHeuristic-Algorithm Services Unique Key-Pair Designator—to Skynet LevelTwo Encryption Circuitry 120 and where the corresponding pseudo-privatekey and unique key-pair designator is delivered to Homeland SecurityLevel Two DEcryption circuitry 128 (in one instance Homeland SecurityLevel Two DEcryption circuitry 128 finds the corresponding decryptionkey via use of a received unique key-pair designator (e.g.,Heuristic-Algorithm-Services Unique Key-Pair Designator as describedherein))).

Other operations of FIG. 4 depict other system/operational descriptionsof implementations as described herein.

Referring now to FIG. 5, FIG. 2, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 5shows that operation 204—decrypting at least a part of the level-twoencrypted output of the surveillance device with a level-two decryptionkey that is practicably inaccessible by a level-two encryptionentity—may include a number of alternate/additional componentoperations. Operation 500 depicts receiving the level-two decryption keyinaccessible by a level-two encryption entity from a level-two key-pairgeneration entity (e.g., Level-Two Key Pair Designator ReceptionCircuitry D108 receives a DEcryption key (e.g., Heuristic-AlgorithmServices Pseudo-Public DEcryption Key D102) inaccessible by Skynet LevelTwo Encryption Circuitry 120, from Heuristic-Algorithm Services Key-PairGeneration Automation 127, where the Heuristic-Algorithm ServicesKey-Pair Generation Automation 127 is such that the decryption key thatwould pair with the encryption that was used by Skynet Level TwoEncryption Circuitry 120 to produce Level-Two Encrypted CCD Output 121is isolated (e.g., by hardware arranged such that only encryption keysmay be transmitted out to Skynet Level Two Encryption Circuitry 120(e.g., only encryption bits have lines that connect with thetransmission automation “facing” Skynet Level Two Encryption Circuitry120 or by automation that securely partitions any decryption key beforeits corresponding encryption key is sent beyond the confines ofHeuristic-Algorithm Services Key-Pair Generation Automation 127))).

FIG. 5 further illustrates that operation 500—receiving the level-twodecryption key inaccessible by a level-two encryption entity from alevel-two key-pair generation entity—may include a number ofalternate/additional component operations. Operation 502 depictsreceiving a level-two key pair designator from the level-two key-pairgeneration entity (e.g., Level-Two Key Pair Designator ReceptionCircuitry D108 receives a decryption key (e.g., Heuristic-AlgorithmServices Pseudo-Private DEcryption Key D102), where the receiveddecryption key (e.g., A Heuristic-Algorithm Services Pseudo-PrivateDEcryption Key) is inaccessible by Skynet Level Two Encryption Circuitry120, along with Unique Heuristic Algorithm Services Key-Pair DesignatorD110, from Heuristic-Algorithm Services Key-Pair Generation Automation127, where the Heuristic-Algorithm Services Key-Pair GenerationAutomation 127 is such that the decryption key that would pair with theencryption key delivered to Skynet Level Two Encryption Circuitry 120 isisolated (e.g., by hardware arranged such that only encryption keys maybe transmitted out to Skynet Level Two Encryption Circuitry 120 (e.g.,only encryption bits have lines that connect with the transmissionautomation “facing” Skynet Level Two Encryption Circuitry 120 or byautomation that securely partitions any decryption key before itscorresponding encryption key is sent beyond the confines ofHeuristic-Algorithm Services Key-Pair Generation Automation 127); in oneinstance, Level-Two Sighted Decryption Circuitry D100 of HomelandSecurity Level Two DEcryption Circuitry 128 uses the received UniqueHeuristic Algorithm Services Key-Pair Designator D110 to match with alike Unique Heuristic Algorithm Services Key-Pair Designator received ina packet from Pre-Crime Repository 122 to retrieve/utilizeHeuristic-Algorithm Services Pseudo-Private Decryption Key D102 as theright key to use for decrypting that which was encrypted with theHeuristic-Algorithm Services Pseudo-Public Encryption Key that was usedto create Level Two Encrypted CCD Output 121)).

Other operations of FIG. 5 depict other system/operational descriptionsof implementations as described herein.

Referring now to FIG. 6, FIG. 2, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 6shows that operation 204—decrypting at least a part of the level-twoencrypted output of the surveillance device with a level-two decryptionkey that is practicably inaccessible by a level-two encryptionentity—may include a number of alternate/additional componentoperations. Operation 600 depicts receiving a level-two key pairdesignator from a level-two key-pair generation entity in a form of alevel-two decryption key that may thereafter function as the level-twokey-pair designator (e.g., Level-Two Key Pair Designator ReceptionCircuitry D108 of Homeland Security Level Two DEcryption Circuitry 128receiving the level two decryption key (e.g., Heuristic-AlgorithmServices pseudo-private decryption key D102) itself which willthereafter be used, like trying keys on a keychain, by separateautomation (e.g., Homeland Security Level Two Decryption Circuitry 128)to find the right decryption key that unlocks the encryption key (e.g.,Homeland Security Level Two Decryption Circuitry 128 successively tryingvarious decryption keys against level-two encrypted CCD output 121 untilan acceptable unlocking is detected such as described herein); thusallowing the encryption key to itself function as a sort of key-pairdesignator (e.g., analogous as to what was described in relation to FBIName DE-Obscuring Circuitry 136 above)). In one instance, the separateautomation (e.g., Level-Two Sighted Decryption Circuitry of HomelandSecurity Level-Two DEcryption Circuitry 128) can so decrypt byrecognizing plain text that Skynet Level Two Encryption Circuitry 120appended to level-one encrypted CCD output 118 before Skynet Level TwoEncryption Circuitry 120 created level-two encrypted CCD output 121; inanother instance, the separate automation (e.g., Homeland SecurityLevel-Two DEcryption Circuitry 128) can so decrypt by calculating aresult of a function (e.g., a hashing function) on the to-be-encryptedlevel-one encrypted data (e.g., level-one encrypted CCD output 118), theresult of such function application (e.g., a hash function run on thelevel-one encrypted output to-be-encrypted into level-two encryptedoutput) Skynet Level Two Encryption Circuitry 120 appended to level-oneencrypted CCD output 118 before encrypting to level-two encrypted CCDoutput 121 (in this instance the function (e.g., hashing function) iseither known or derivable by both level-two decryption and encryptionautomation and thus can be calculated by the receiving automation (e.g.,Homeland Security Level-Two DEcryption Circuitry 128) each time suchautomation tries a key on its key chain to see if the output of thefunction application matches (e.g., the result of running the hashingfunction of a particular tried key on a key chain matches that datawhich is appended, say, as the last 8000 bits, or 80000 bits, etc. ofdata).

Operation 602 depicts decrypting at least a part of a level-twoencrypted output of the surveillance device via combination with otherinformation not present in the level-two encrypted output of thesurveillance device (e.g., Level-Two Sighted DEcryption Circuitry D100of Homeland Security Level Two DEcryption Circuitry 128 decrypting oneor more parts or sub-parts of Level-Two Encrypted CCD Output121—received from Pre-Crime Repository 122—with a level-two decryptionkey (e.g., Heuristic Algorithm Services Pseudo-Private DEcryption KeyD102) which Skynet Level Two Encryption Circuitry 120 has/had nopracticable way of knowing such that the parts encrypted by Skynet LevelTwo Encryption Circuitry 120 would be substantially unusable absent thecorresponding level-two decryption key (e.g., the corresponding pairedpseudo-private decryption key generated by Heuristic-Algorithm ServicesKey-Pair Generation Automation 127)).

Operation 602—decrypting at least a part of a level-two encrypted outputof the surveillance device via combination with other information notpresent in the level-two encrypted output of the surveillance device—mayinclude a number of alternate/additional component operations. Operation604 depicts receiving a level-two decryption key inaccessible by alevel-two encryption entity from a level-two key-pair generation entity(e.g., Level-Two Key Pair Designator Reception Circuitry D108 ofHomeland Security Level Two Encryption Circuitry 128 receiving fromHeuristic-Algorithm Services Key-Pair Generation Automation 127 thelevel two decryption key (e.g., Heuristic Algorithm ServicesPseudo-Private DEcryption Key D102) which will thereafter be used, liketrying keys on a keychain, by separate automation (e.g., HomelandSecurity Level-Two DEcryption Circuitry 128) to find the rightdecryption key that unlocks the encryption key; thus allowing theencryption key to itself function as a sort of key-pair designator(e.g., analogous to such as what was described in relation to FBI NameDE-Obscuring Circuitry 136 or elsewhere herein)).

Operation 604—receiving a level-two decryption key inaccessible by alevel-two encryption entity from a level-two key-pair generationentity—may include a number of alternate/additional componentoperations. Operation 606 depicts receiving a level-two key pairdesignator from a pre-event repository (e.g., Level-Two Key PairDesignator Reception Circuitry D108 of Homeland Security Level TwoDEcryption Circuitry 128 receiving from a packet from PreCrimeRepository 122 having Level-Two Encrypted CCD Output 121—along with aunique level-two key—pair designator (e.g., unique Heuristic AlgorithmService Key Pair Designator D110—at or around a logically subsequenttime when the corresponding (but unknown to Skynet Level Two EncryptionCircuitry 120) decryption key (e.g., Heuristic Algorithm ServicesPseudo-Private DEcryption Key)—along with Unique Heuristic-AlgorithmServices Key Pair Designator D110 is sent by Heuristic-AlgorithmServices Key-Pair Generation Automation 127 to Homeland Security LevelTwo DEcryption Circuitry 128, the corresponding encryption key (e.g.,Heuristic-Algorithm Services Pseudo-Public Encryption key) of which wasused by Skynet Level Two Encryption Circuitry 120 to create Level-TwoEncrypted CCD Output 121)).

Operation 608 depicts receiving a level-two key pair designator from alevel-two key-pair generation entity in a form of a level-two decryptionkey that may thereafter function as the level-two key-pair designator(e.g., Level-Two Key-Pair Designator Reception Circuitry D108 ofHomeland Security Level Two DEcryption Circuitry 128 receiving fromHeuristic-Algorithm Services Key-Pair Generation Automation 127 thelevel two decryption key (e.g., Heuristic Algorithm ServicesPseudo-Private DEcryption Key D102) itself which will thereafter beused, like trying keys on a keychain, by separate automation (e.g., byLevel-Two Sighted Decryption Circuitry D100 of Homeland SecurityLevel-Two DEcryption Circuitry 128) to find the right decryption keythat unlocks the encryption key (e.g., the Heuristic Algorithm ServicesPseudo-Private key D102 that will unlock encryption done with theHeuristic Algorithm Services Pseudo-Public Encryption Key); thusallowing the decryption key to itself function as a sort of key-pairdesignator (e.g., such as was described in relation to FBI NameDE-Obscuring Circuitry 136 above and elsewhere herein)). In oneinstance, the automation (e.g., Homeland Security Level-Two DEcryptionCircuitry 128) can so decrypt by recognizing plain text that SkynetLevel Two Encryption Circuitry 120 appended to level-one encrypted CCDoutput 118 before encrypting to Level-Two Encrypted CCD Output 121; inanother instance, the automation (e.g., Homeland Security Level-TwoDEcryption Circuitry 128) can so decrypt by calculating a result of afunction (e.g., a hashing function), which result Skynet Level TwoEncryption Circuitry 120 appended to Level-One Encrypted CCD Output 118before encrypting to Level-Two Encrypted CCD Output 121 (in thisinstance the function (e.g., hashing function) is either known orderivable by both level-two decryption and encryption automation); suchappended data can be checked and re-checked as each key on the key chainis tried.

Other operations of FIG. 6 depict other system/operational descriptionsof implementations as described herein.

Referring now to FIG. 7, FIG. 2, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 7shows that operation 206—transmitting a level-one encrypted output ofthe surveillance device—may include a number of alternate/additionalcomponent operations. Operation 700 depicts transmitting a level-oneencrypted output of the surveillance device in conjunction with asurveillance device identifier (e.g., Level-Two DEcrypted TransmissionCircuitry D104 of Homeland Security Level-Two DEcryption Circuitry 128transmitting Level-Two DEcrypted-Level-One Encrypted CCD Output 129(e.g., DEcrypted with Heuristic-Algorithm Services Pseudo-PrivateDEcryption Key D102 by Level-Two Sighted DEcryption Circuitry D100 ofHomeland Security Level-Two DEcryption Circuitry 128), UniqueHeuristic-Algorithm-Services Key Pair Designator D110, and some type ofsurveillance device identifier (e.g., “Skynet Security Camera Alpha”) toFBI Level-One DEcryption Circuitry 130).

FIG. 7 further illustrates that operation 700 transmitting a level-oneencrypted output of the surveillance device in conjunction with asurveillance device identifier—may include a number ofalternate/additional component operations. Operation 702 showstransmitting a level-one encrypted output of the surveillance device inconjunction with an encrypted version of the surveillance deviceidentifier (e.g., Level-Two Decrypted Transmission Circuitry D104 ofHomeland Security Level Two DEcryption Circuitry 128 transmitting anoutput that Level-Two Sighted Decryption Circuitry D100 of Skynet LevelTwo Encryption Circuitry 128 has DEcrypted to Level-Two Decrypted-LevelOne Encrypted CCD Output 129 with the requisite decryption keyinaccessible by Skynet Level Two Encryption Circuitry 120 in conjunctionwith an encrypted surveillance device identifier (e.g.,“Encrypted-Camera-ID”—the encrypted version of “skynet security cameraalpha” produced by Skynet Name Obscuring Unit 106 and received byLevel-Two Decrypted Transmission Circuitry D104 in conjunction withLevel-Two Encrypted CCD Output 121 that was also received by Level-TwoDecrypted Transmission Circuitry D104 from Pre-Crime Repository122))—may include a number of alternate/additional component operations.Operation 704 depicts receiving an encrypted version of the surveillancedevice identifier (e.g., Decrypted Transmission Circuitry D104 ofHomeland Security Level Two DEcryption Circuitry 128 receiving anencrypted identifier (e.g., “Encrypted Camera ID from Pre-CrimeRepository 122 which itself received the encrypted identifier, throughvarious intermediaries, from Skynet Name Obscuring Unit 106)).

Continuing to refer to FIG. 7, Fig. A1, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 7further shows that operation 702 transmitting a level-one encryptedoutput of the surveillance device in conjunction with an encryptedversion of the surveillance device identifier—may include a number ofalternate/additional component operations. Operation 706 depictsreceiving an encryption of at least a part of a version of thesurveillance device identifier that was encrypted with a name-obscuringencryption key whose decryption key is inaccessible by a level-oneencryption entity (e.g., Homeland Security Level Two DEcryptionCircuitry 128 receiving from Pre-Crime Repository 122 a version of“Skynet Security Camera Alpha” (e.g., “Encrypted-Camera-ID”) that wasencrypted with a pseudo public key generated by Camera-to-Obscure CoCircuitry 104 as described herein; as also described herein Pre-CrimeRepository 122 has previously received the encrypted device identifierfrom Skynet Name Obscuring Unit 106, through various intermediaries,prior to transmitting the encrypted device identifier to HomelandSecurity Level Two DEcryption Circuitry 128). Operation 708 depictstransmitting the encryption of at least the part of the version of thesurveillance device identifier in conjunction with the level-oneencrypted output of the surveillance device (e.g., Level-Two DEcryptedTransmission Circuitry D104 of Homeland Security Level Two DEcryptionCircuitry 128 transmitting a version of a packet—containing the string“Encrypted-Camera-ID+16 June 2014; Time 10:00 a.m.-11:00 a.m.”, linkedwith at least a part of Level-Two DEcrypted-Level-One Encrypted CCDOutput 129—to FBI Level-One DEcryption Circuitry 130).

Continuing to refer to FIG. 7, FIG. 2, and FIG. 1, such figuresillustrate system/operational descriptions of implementations. FIG. 7shows that operation 206—transmitting a level-one encrypted output ofthe surveillance device—may include a number of alternate/additionalcomponent operations. Operation 710 depicts transmitting a level-oneencrypted output of the surveillance device to level-one decryptioncircuitry (e.g., Level-Two DEcrypted Transmission Circuitry D104 ofHomeland Security Level Two DEcryption Circuitry 128 transmittingLevel-Two DEcrypted-Level-One Encrypted CCD output 129 of Camera 102 tolevel-one decryption circuitry (e.g., FBI Level-One DEcryption Circuitry130)).

Other operations of FIG. 7 depict other system/operational descriptionsof implementations as described herein.

IV. Implementations May Be Context Dependent

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware in one or moremachines, compositions of matter, and articles of manufacture, limitedto patentable subject matter under 35 USC 101. Hence, there are severalpossible vehicles by which the processes and/or devices and/or othertechnologies described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary. Those skilled in the art willrecognize that optical aspects of implementations will typically employoptically-oriented hardware, software, and or firmware.

V. Tools Allowing Automated/Mechanical Transition from Higher LevelInstructions to Circuitry and/or Direct Circuitry Implementations

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operation described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled//implemented/translated/converted into a high-level descriptor language(e.g., initially implementing described technologies in C or C++programming language and thereafter converting the programming languageimplementation into a logic-synthesizable language implementation, ahardware description language implementation, a hardware designsimulation implementation, and/or other such similar mode(s) ofexpression). For example, some or all of a logical expression (e.g.,computer programming language implementation) may be manifested as aVerilog-type hardware description (e.g., via Hardware DescriptionLanguage (HDL) and/or Very High Speed Integrated Circuit HardwareDescriptor Language (VHDL)) or other circuitry model which may then beused to create a physical implementation having hardware (e.g., anApplication Specific Integrated Circuit). Those skilled in the art willrecognize how to obtain, configure, and optimize suitable transmissionor computational elements, material supplies, actuators, or otherstructures in light of these teachings.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof, limited to patentablesubject matter under 35 U.S.C. 101. In an embodiment, several portionsof the subject matter described herein may be implemented viaApplication Specific Integrated Circuits (ASICs), Field ProgrammableGate Arrays (FPGAs), digital signal processors (DSPs), or otherintegrated formats. However, those skilled in the art will recognizethat some aspects of the embodiments disclosed herein, in whole or inpart, can be equivalently implemented in integrated circuits, as one ormore computer programs running on one or more computers (e.g., as one ormore programs running on one or more computer systems), as one or moreprograms running on one or more processors (e.g., as one or moreprograms running on one or more microprocessors), as firmware, or asvirtually any combination thereof, limited to patentable subject matterunder 35 U.S.C. 101, and that designing the circuitry and/or writing thecode for the software and or firmware would be well within the skill ofone of skill in the art in light of this disclosure. In addition, thoseskilled in the art will appreciate that the mechanisms of the subjectmatter described herein are capable of being distributed as a programproduct in a variety of forms, and that an illustrative embodiment ofthe subject matter described herein applies regardless of the particulartype of signal bearing medium used to actually carry out thedistribution. Examples of a signal bearing medium include, but are notlimited to, the following: a recordable type medium such as a floppydisk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk(DVD), a digital tape, a computer memory, etc.; and a transmission typemedium such as a digital and/or an analog communication medium (e.g., afiber optic cable, a waveguide, a wired communications link, a wirelesscommunication link (e.g., transmitter, receiver, transmission logic,reception logic, etc.), etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, Verizon, AT&T, etc.), or (g) a wired/wireless services entity(e.g., Sprint, AT&T, Verizon, etc.), etc.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and/or distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, or, in many ifnot all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, or donot refer to products or compounds for which knowledge of one or moretrade secrets is required in order to divine their meaning. Alltrademarks referenced in this application are the property of theirrespective owners, and the appearance of one or more trademarks in thisapplication does not diminish or otherwise adversely affect the validityof the one or more trademarks. All trademarks, registered orunregistered, that appear in this application are assumed to include aproper trademark symbol, e.g., the circle R or bracketed capitalization(e.g., [trademark name]), even when such trademark symbol does notexplicitly appear next to the trademark. To the extent a trademark isused in a descriptive manner to refer to a product or process, thattrademark should be interpreted to represent the corresponding productor process as of the date of the filing of this patent application.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

What is claimed is: 1.-41. (canceled)
 42. A system comprising: level-twodecryption circuitry structured to interface with a pre-eventrepository; said level-two decryption circuitry structured to interfacewith level-two key pair generation automation; and said level-twodecryption circuitry structured to interface with level-one decryptioncircuitry.
 43. The system of claim 42 wherein a pre-event repositorycomprises: a pre-event repository structured to store a doubly-encryptedlockbox.
 44. The system of claim 43 wherein pre-event repositorystructured to store a doubly-encrypted lockbox comprises: a pre-eventrepository structured to store a doubly-encrypted output of asurveillance device.
 45. The system of claim 44 wherein pre-eventrepository structured to store a doubly-encrypted output of asurveillance device comprises: a pre-event repository double-locked boxstorage engine operably coupled with a memory of the a pre-eventrepository.
 46. The system of claim 42 wherein level-two decryptioncircuitry structured to interface with level-one decryption circuitrycomprises: said level-two decryption circuitry structured to store aunique key-pair designator associated with the level-two key pairgeneration automation.
 47. The system of claim 46 wherein level-twodecryption circuitry structured to store a unique key-pair designatorassociated with the level-two key pair generation automation comprises:said level-two decryption circuitry structured to store a decryption keyassociated with a paired encryption key (a) generated by the level-twokey pair generation automation and (b) kept private from level-twoencryption automation by an architecture associated the level-two keypair generation automation.
 48. The system of claim 46 wherein level-twodecryption circuitry structured to store a unique key-pair designatorassociated with the level-two key pair generation automation comprises:said level-two decryption circuitry structured to store a uniquelevel-two key-pair designator generated by the level-two key pairgeneration automation.
 49. The system of claim 46 wherein level-twodecryption circuitry structured to store a unique key-pair designatorassociated with the level-two key pair generation automation comprises:level-two key-pair designator reception circuitry structured to receivea unique level-two key-pair designator generated by the level-two keypair generation automation.
 50. The system of claim 46 wherein level-twodecryption circuitry structured to store a unique key-pair designatorassociated with the level-two key pair generation automation comprises:level-two sighted decryption circuitry structured to recognize a correctdecryption key associated with a level-two encryption of a level-oneencrypted output of a surveillance device by comparison of at least oneof clear text or a hash appended to the level-one encrypted output of asurveillance device by the level-two encryption circuitry prior to thelevel-two encryption with a paired encryption key generated by thelevel-two key pair generation automation.
 51. The system of claim 46wherein level-two decryption circuitry structured to store a uniquekey-pair designator associated with the level-two key pair generationautomation comprises: level-two sighted decryption circuitry structuredto recognize a correct decryption key associated with a level-twoencryption of a level-one encrypted output of a surveillance device bycomparison a unique key pair designator received from the a pre-eventrepository against a unique key pair designator received from thelevel-two key pair generation automation.
 52. The system of claim 42wherein level-two decryption circuitry structured to interface withlevel-one decryption circuitry comprises: said level-two decryptioncircuitry structured to transmit a level-one encrypted output asurveillance device to the level-one decryption circuitry.
 53. Thesystem of claim 52 wherein level-two decryption circuitry structured totransmit a level-one encrypted output a surveillance device to thelevel-one decryption circuitry comprises: level-two sighted decryptioncircuitry structured to apply a level-two decryption key against alevel-two encrypted output of a surveillance device to produce thelevel-one encrypted output of the surveillance device.
 54. The system ofclaim 53 further comprising: level-two decrypted transmission circuitrystructured to receive the level-one encrypted output of the surveillancedevice from the level-two sighted decryption circuitry.
 55. The systemof claim 54 further comprising: said level-two decrypted transmissioncircuitry structured to append a version of a surveillance deviceidentifier to the level-one encrypted output of the surveillance device.56. The system of claim 55 further comprising: said level-two decryptedtransmission circuitry structured to append an encrypted version of asurveillance device identifier to the level-one encrypted output of thesurveillance device.
 57. The system of claim 55 further comprising: saidlevel-two decrypted transmission circuitry structured to transmit atleast one of a version of a surveillance device identifier or thelevel-one encrypted output of the surveillance device to the level-onedecryption circuitry.
 58. A method comprising: receiving a level-twoencrypted output of a surveillance device that is the result of alevel-two blind encryption done on a level-one encrypted output of thesurveillance device; and applying a decryption key appropriate to thelevel-two blind encryption to the level-two encrypted output of asurveillance device that is the result of the level-two blind encryptiondone on the level-one encrypted output of the surveillance device. 59.The method of claim 58 wherein applying a decryption key appropriate tothe level-two blind encryption to the level-two encrypted output of asurveillance device that is the result of the level-two blind encryptiondone on the level-one encrypted output of the surveillance devicecomprises: determining the decryption key appropriate to the level-twoblind encryption.
 60. The method of claim 59 wherein determining thedecryption key appropriate to the level-two blind encryption comprises:applying an candidate decryption key to level-two encrypted output of asurveillance device that is the result of the level-two blind encryptiondone on the level-one encrypted output of the surveillance device; anddetermining whether or not a result of an application of the candidatedecryption key to the level-two encrypted output of a surveillancedevice that is the result of the level-two blind encryption done on thelevel-one encrypted output of the surveillance device matches a datablock associated with a level two encryption entity; and denoting thecandidate decryption key as that appropriate to level-two blindencryption done on the level-one encrypted output of the surveillancedevice if the result of the application of the candidate decryption keymatches the data block associated with the level two encryption entity.61. The method of claim 60 wherein determining whether or not a resultof an application of the candidate decryption key to the level-twoencrypted output of a surveillance device that is the result of thelevel-two blind encryption done on the level-one encrypted output of thesurveillance device matches a data block associated with a level twoencryption entity comprises: determining whether or not a result of anapplication of the candidate decryption key to the level-two encryptedoutput of a surveillance device that is the result of the level-twoblind encryption done on the level-one encrypted output of thesurveillance device matches a clear text string associated with a leveltwo encryption entity; or determining whether or not a result of anapplication of the candidate decryption key to the level-two encryptedoutput of a surveillance device that is the result of the level-twoblind encryption done on the level-one encrypted output of thesurveillance device matches a result of a hashing function associatedwith an encryption performed by a level two encryption entity.
 62. Themethod of claim 59 wherein determining the decryption key appropriate tothe level-two blind encryption comprises: comparing a unique key pairdesignator received from a pre-event repository against at least oneunique key pair designator received from a level-two key pair generationautomation; and denoting a decryption key associated with the at leastone unique key pair designator received from the level-two key pairgeneration automation that matches the unique key pair designatorreceived from the a pre-event repository.
 63. A system comprising:circuitry for receiving a level-two encrypted output of a surveillancedevice that is the result of a level-two blind encryption done on alevel-one encrypted output of the surveillance device; and circuitry forapplying a decryption key appropriate to the level-two blind encryptionto the level-two encrypted output of a surveillance device that is theresult of the level-two blind encryption done on the level-one encryptedoutput of the surveillance device.